Calling the "Bypass Screening Policy" API endpoint triggers a new transaction, with the API user as the initiator, bypassing the screening policy check

This endpoint is restricted to Admin API users and is only applicable to outgoing transactions.

POST /screening/transaction/{txId}/bypass_screening_policy

TypeScript

TypeScript

const response: Promise<FireblocksResponse<CreateTransactionResponse>> = fireblocks.compliance.retryRejectedTransactionBypassScreeningChecks(complianceApiRetryRejectedTransactionBypassScreeningChecksRequest);

201

{
  "id": "<string>",
  "status": "<string>",
  "systemMessages": [
    {
      "type": "WARN",
      "message": "Slow transaction processing. Outgoing transactions might be stuck."
    }
  ]
}

Headers

Idempotency-Key · string

A unique identifier for the request. If the request is sent multiple times with the same idempotency key, the server will return the same response as the first request. The idempotency key is valid for 24 hours.

Path Parameters

txId · string · required

The transaction id that was rejected by screening checks

Response

201

application/json

A transaction object

id · string

The ID of the transaction.

status · string

The primary status of the transaction. For details, see [Primary transaction statuses.] (https://developers.fireblocks.com/reference/primary-transaction-statuses)

systemMessages · object[]

Show child attributes